Notes/Domino 6 and 7 Forum : RE: Server To Server Migration GroupWise to Notes with CMT of Binary Tree

We have migrated 50 of 1000 groupwise users using the binary tree tool. We are doing server to server for the mail files, and end user for address books and archives.

We had some problems, which Binary Tree tech support was very helpful with. A user had over 3GB of mail and nested folders the longest of which turned out to be over the 130 char limit imposed by notes.

Our project is halted now because of issues with DOLS. I am hoping those can be resolved and we can finish the project.

It is very important, or it was for us and our environment to create a checklist of all the steps necessary to migrate a user. There was a lot involved. Here are some of the steps we took to try and ensure a correct migration. (not all of it came across, because of space limitations, but you get the idea. I suggest that you test, test, test!

Migration Checklist for GroupWise Users to Notes

User Name______________________________ GW ID: _____________ Phone Ext._______

Migrator Name:________________________________ Date of Migration:_________________

PART I – MIGRATION PREPARATIONS

Before You Begin!!

___ Does User own any resources (conference rooms, etc.)?___________ If so, please add names of resources here:_________________________________________________________________

___ If user owns resources, the user’s GW account must be maintained after migration. DO NOT REMOVE GW ACCOUNT!!

___ User must be registered in Notes and have a mail file prior to migrating his/her account.
* Users outside of the original pilot will need to be re-registered w/ a text file!!

___ The “Forwarding Address” MUST BE REMOVED from the persion document prior to migration!!

GroupWise Preparation:

___ Using GWCheck utility, run an “Analyze & Fix” on structure and contents of the user database (once you open the utility, select “retrieve” and use the migoptions.opt file to pull in all information except the userid).

___ Double click on NWAdmin32 icon to open NetWare/GW Administration.

___ In the GroupWise View, Locate name of user to be migrated in list of GroupWise users by clicking on Domain icon or the Post Office Icon if you know which PO they are in (all users show up at the bottom).

___ Double click on user name to open the Details of their NW/GW account.

___ Locate and click on the GroupWise Account tab by scrolling down through the tabs on the right side.

___ While on the GroupWise Account screen, note the File ID for this user ________.

___ Click on the Change GroupWise Password button on this screen.

___ Click in the Clear GroupWise Password checkbox then click on OK.

___ Click on the Change GroupWise Password button again.

___ Enter new password (use new Notes password) and click OK.
___ Look under GroupWise Distribution Lists Tab and write down membership listing:

___ Click on the Cancel button to exit user details.

Setting up External User Account in GroupWise

___ While still in NWAdmin32, in the GroupWise View, Click on the Plus (+) next to the Internet Domain, then on HMMAIL.

___ Right-click HMMAIL and select Create.

___ Select External User and click OK.

___ Put in the name to be used in internet addressing (i.e. Firstname_Lastname) in the User Name field and check “Define additional Properties” before selecting “Create”.

___ Enter the user’s first name and last name on the Information Tab, then go to the GroupWise Distribution Lists tab and add them to the groups defined above.

___ If this is being done more than a few hours in advance, go to the GroupWise Account tab and set their visibility to None (so that people don’t begin sending mail to their new account).

Create a Forwarding Rule in GroupWise Account

___ Open GroupWise as user being migrated (using newly assigned password).

___ Click on Tools, then Rules and select New.

___ Name Rule “Forward to Notes” and check all items Received and select all Item Types.

___ Click Add Action button and select Forward.

___ Under the “To” field, put in the new External User Account (find it in the address book if the visibility is set to “System”).

___ Check to make sure that there are no “Stop” rules in affect for the user.
Check Location of GW Archives

___ Click on Tools, Options, Environment, and select the File Locations Tab. Path to Archive: ______________________________________________________. This information will be required to migrate archives. If the archive directory is a local drive (c, d, or e), their archives will have to be moved prior to migration.

Assigning NotesMig Proxy Access to GroupWise Account

___ Click on the Security icon (still under Tools|Options).

___ Click on the Proxy Access tab and search for the Migration Notes user in the drop down list.

___ Click on Add User button and then give the migration notes user all rights to the GroupWise account by placing a checkmark in each box.

___ Click OK then Close.

___ Close and Exit GW.

PART II – SERVER TO SERVER MIGRATION

Accessing the CMT Migration Tool

___ Open Domino Administration client software using the Administrator signon.

___ Click on the Files tab and locate the CMT database in the list.

___ Double click on the CMT database to open it.

___ Press the Escape button to exit the Introduction screen.

___ Click on the Add Users tab.

___ Click on the option to Import from foreign Directory then click on GroupWise.

___ Click on the Next button.

___ Click on Migrate all boxes then click on the Next button.

___ Select the user(s) from the list.

___ Type in the password for notesmig. This will bring up list of GroupWise users.

___ Locate and click on the user to migrate and then click on the Next button.

___ Click on the Import Users from GroupWise button.

___ Wait until process is finished.

___ When finished, click on Next then on Finish.

___ On the next screen that appears click on the Server Migration tab.

___ Click on GroupWise 5.x then on Migrate selected.

___ Click on Next button.

___ Click on Select Users button then on OK.

___ Click on Migrate Users button then wait for migration to finish. This process could take as much as 1 hour to complete.

___ Update migration spreadsheet in .........\Migration Documentation w/ completion information.

___ Call user being migrated with status of mailbox migration when server to server has been completed. Let them know that their archives/personal contacts will be completed within 3 days and they will receive a follow-up E-mail regarding this.

___ Send E-mail communication #4 located in .........iNotes\Migration Documentation.
PART III – END USER MIGRATION OF ARCHIVES/CONTACTS

Migration of Personal Address Book and Archives:

___ Check above to be sure that archives are located on a network drive and that your Notesmig ID is mapped the same as the user you are migrating (i.e. V: is mapped to the same drive as their Post Office).

___ Run GWCheck on user’s archives. The path will be v:\gwarchiv\ofXXXarc (where XXX is the user’s FID). Select to Analyze and Fix on the structure of both User and Message databases.

___ Open GW as user being migrated (and make sure that you can access the archives by clicking File, Open Archive).

___ Prepare the workstation by copying G:\NAMES.NSF over the top of c:\Program Files\lotus\notes\data\names.nsf. (makes sure you have a clean names.nsf)

___ Check to make sure C:\GWARCHIV does not exist.

___ Open the Notes Client as ADMIN using Office (migration) location profile and Edit the current location profile to match the user that you are migrating (ie. Mail file should be his shortname.nsf, id file should point to the user’s ID file on E:\IDFILES), save the changes, and test that you can open their mailbox. Once finished, make sure the local contacts are empty, then close Notes.

___ Open Domino Administrator and click on the Files Tab.

___ Select the CMT directory on the left side of the screen and open the CMT2003 database.

___ Click on the “People by Registration status” on the left to see the list of users.

___ Once they appear in your registration screen, double click on the name of the user you are going to migrate and, in the End User Migration Settings, click on “Send Migration Document”.

___ Once migration document is sent, get back into Notes as the user being migrated, and make sure GW is also open under the same user’s ID.

___ When you open user’s Notes mail, if alarms appear, mark them all as “Done”.

___ You will see a mail message from the Admin for migrating your mail. Open the mail message from Admin and execute the “Start Migration” button and answer “Yes” to any messages regarding security or certificates. The migration process will build a C:\Gwarchiv.nsf file on the local PC, and add all personal contacts to the local NAMES.NSF file.

___ Delete Messages from Admin/CMT/Binary Tree regarding migration/archives.

___ Clean up “contacts” to remove GW users (leaving only internet addresses and personal groups).

___ In order to update the iNotes “Contacts”, you must be in the user’s mailbox and choose Actions | Syncronize Address Book to transfer contact information.

___ Rename local copy of C:\GWARCHIV.nsf to C:\GWARCHIVshortname.

___ Make sure you have a drive mapped to share on notes server and copy the c:\gwarchiv.nsf file to the archive directory on notes server (ie. If X: is the root of notes server\E$, then the path would be X:\NOTES\DATA\ARCHIVE and the file would be renamed using a_ and the user’s shortname. An example would be a_suserg1.nsf).

___ Open archive file and see if it matches the GW archives.

___ Open mail file and select Actions|Edit Offline Configuration. Under the Sync Options tab, after the name of the mail file, put in a semi-colon, then add the path and name of the archive file from the data directory (ie. ;archive\a_shortname.nsf)

___ Get back into Notes as ADMIN using the Office (Network) location profile and send newly migrated user a link to his/her archive file.

___ Remove GW UserID from distribution lists in NWADMIN32 by selecting their UserID, going to the GroupWise Distribution Lists tab, highlighting all groups, and selecting “Delete”.

___ Rename Last Name on “Identification” tab to GW-lastname, and on the “GroupWise Account Tab”, rename the Mailbox ID to GW-userid.

___ Update Migration spreadsheet in .......Migration Documentation with completion status on GW Archives/Personal Contacts.

Notes/Domino 6 and 7 Forum

Document Options

Search this forum

Forum views and search

Member Tools

RSS Feeds